add DJANGO_CONFIGURATION_HOOK as optional parameter to allow customly… #1002
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I guess you can close this now? ;-) |
|
I guess so : ) |
JulianFeinauer
force-pushed
the
feature/1001-custom-django-settings
branch
from
0df61b3 to
16db732
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… configured settings instances
This is a first draft implementation for #1001 to have a starting point for a discussion.
See here for how this would be applied: https://github.com/pragmaticindustries/open-machine-plattform/tree/feature/new-launcher-with-pytest-fixes
Especially https://github.com/pragmaticindustries/open-machine-plattform/blob/feature/new-launcher-with-pytest-fixes/pytest_setup.py
which is the hook that would be called and would internally call
settings.configure({...})to prepare a validsettingssingleton for later.